Create a GitHub release when a version tag is published - #2
Merged
Conversation
Tagging published the package to npm but never created a release, so the repo's Releases page stayed on the previous version. The PHP SDK's workflow already did this; this brings Node.js in line. Notes are auto-generated from merged PRs and can be edited afterwards. The job now needs contents: write to create the release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tagging published the package to npm but never created a GitHub release, so the repo's Releases page kept showing the previous version even though the new one had shipped.
The PHP SDK's workflow already had this step — this brings Node.js in line, so all four SDKs behave the same.
Changes
Create GitHub releasestep (softprops/action-gh-release@v2) after the publish step.contentspermission fromreadtowrite, which the action needs.CapSkip Node.js SDK <tag>, matching the existing convention.Release notes are auto-generated from merged PRs and can be edited afterwards.
Note
The v1.1.0 release was created by hand, so this only affects future tags.